<!DOCTYPE html>
<html lang="en-us">
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    
<meta charset="UTF-8">
<title>Install Elasticsearch with RPM | Elasticsearch Guide [7.7] | Elastic</title>
<link rel="home" href="index.html" title="Elasticsearch Guide [7.7]">
<link rel="up" href="install-elasticsearch.html" title="Installing Elasticsearch">
<link rel="prev" href="deb.html" title="Install Elasticsearch with Debian Package">
<link rel="next" href="windows.html" title="Install Elasticsearch with Windows MSI Installer">
<meta name="DC.type" content="Learn/Docs/Elasticsearch/Reference/7.7">
<meta name="DC.subject" content="Elasticsearch">
<meta name="DC.identifier" content="7.7">
<meta name="robots" content="noindex,nofollow">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <script src="https://cdn.optimizely.com/js/18132920325.js"></script>
    <link rel="apple-touch-icon" sizes="57x57" href="/apple-icon-57x57.png">
    <link rel="apple-touch-icon" sizes="60x60" href="/apple-icon-60x60.png">
    <link rel="apple-touch-icon" sizes="72x72" href="/apple-icon-72x72.png">
    <link rel="apple-touch-icon" sizes="76x76" href="/apple-icon-76x76.png">
    <link rel="apple-touch-icon" sizes="114x114" href="/apple-icon-114x114.png">
    <link rel="apple-touch-icon" sizes="120x120" href="/apple-icon-120x120.png">
    <link rel="apple-touch-icon" sizes="144x144" href="/apple-icon-144x144.png">
    <link rel="apple-touch-icon" sizes="152x152" href="/apple-icon-152x152.png">
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-icon-180x180.png">
    <link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
    <link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
    <link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
    <link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
    <link rel="manifest" href="/manifest.json">
    <meta name="apple-mobile-web-app-title" content="Elastic">
    <meta name="application-name" content="Elastic">
    <meta name="msapplication-TileColor" content="#ffffff">
    <meta name="msapplication-TileImage" content="/mstile-144x144.png">
    <meta name="theme-color" content="#ffffff">
    <meta name="naver-site-verification" content="936882c1853b701b3cef3721758d80535413dbfd">
    <meta name="yandex-verification" content="d8a47e95d0972434">
    <meta name="localized" content="true">
    <meta name="st:robots" content="follow,index">
    <meta property="og:image" content="https://www.elastic.co/static/images/elastic-logo-200.png">
    <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
    <link rel="icon" href="/favicon.ico" type="image/x-icon">
    <link rel="apple-touch-icon-precomposed" sizes="64x64" href="/favicon_64x64_16bit.png">
    <link rel="apple-touch-icon-precomposed" sizes="32x32" href="/favicon_32x32.png">
    <link rel="apple-touch-icon-precomposed" sizes="16x16" href="/favicon_16x16.png">
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
    <link rel="stylesheet" type="text/css" href="/guide/static/styles.css">
  </head>

  <!--© 2015-2021 Elasticsearch B.V. Copying, publishing and/or distributing without written permission is strictly prohibited.-->

  <body>
    <!-- Google Tag Manager -->
    <script>dataLayer = [];</script><noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-58RLH5" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
    <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-58RLH5');</script>
    <!-- End Google Tag Manager -->

    <!-- Global site tag (gtag.js) - Google Analytics -->
    <script async src="https://www.googletagmanager.com/gtag/js?id=UA-12395217-16"></script>
    <script>
      window.dataLayer = window.dataLayer || [];
      function gtag(){dataLayer.push(arguments);}
      gtag('js', new Date());
      gtag('config', 'UA-12395217-16');
    </script>

    <!--BEGIN QUALTRICS WEBSITE FEEDBACK SNIPPET-->
    <script type="text/javascript">
      (function(){var g=function(e,h,f,g){
      this.get=function(a){for(var a=a+"=",c=document.cookie.split(";"),b=0,e=c.length;b<e;b++){for(var d=c[b];" "==d.charAt(0);)d=d.substring(1,d.length);if(0==d.indexOf(a))return d.substring(a.length,d.length)}return null};
      this.set=function(a,c){var b="",b=new Date;b.setTime(b.getTime()+6048E5);b="; expires="+b.toGMTString();document.cookie=a+"="+c+b+"; path=/; "};
      this.check=function(){var a=this.get(f);if(a)a=a.split(":");else if(100!=e)"v"==h&&(e=Math.random()>=e/100?0:100),a=[h,e,0],this.set(f,a.join(":"));else return!0;var c=a[1];if(100==c)return!0;switch(a[0]){case "v":return!1;case "r":return c=a[2]%Math.floor(100/c),a[2]++,this.set(f,a.join(":")),!c}return!0};
      this.go=function(){if(this.check()){var a=document.createElement("script");a.type="text/javascript";a.src=g;document.body&&document.body.appendChild(a)}};
      this.start=function(){var a=this;window.addEventListener?window.addEventListener("load",function(){a.go()},!1):window.attachEvent&&window.attachEvent("onload",function(){a.go()})}};
      try{(new g(100,"r","QSI_S_ZN_emkP0oSe9Qrn7kF","https://znemkp0ose9qrn7kf-elastic.siteintercept.qualtrics.com/WRSiteInterceptEngine/?Q_ZID=ZN_emkP0oSe9Qrn7kF")).start()}catch(i){}})();
    </script><div id="ZN_emkP0oSe9Qrn7kF"><!--DO NOT REMOVE-CONTENTS PLACED HERE--></div>
    <!--END WEBSITE FEEDBACK SNIPPET-->

    <div id="elastic-nav" style="display:none;"></div>
    <script src="https://www.elastic.co/elastic-nav.js"></script>

    <!-- Subnav -->
    <div>
      <div>
        <div class="tertiary-nav d-none d-md-block">
          <div class="container">
            <div class="p-t-b-15 d-flex justify-content-between nav-container">
              <div class="breadcrum-wrapper"><span><a href="/guide/" style="font-size: 14px; font-weight: 600; color: #000;">Docs</a></span></div>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div class="main-container">
      <section id="content">
        <div class="content-wrapper">

          <section id="guide" lang="en">
            <div class="container">
              <div class="row">
                <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                  <!-- start body -->
                  <div class="page_header">
<strong>IMPORTANT</strong>: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
<a href="../current/index.html">current release documentation</a>.
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="setup.html">Set up Elasticsearch</a></span>
»
<span class="breadcrumb-link"><a href="install-elasticsearch.html">Installing Elasticsearch</a></span>
»
<span class="breadcrumb-node">Install Elasticsearch with RPM</span>
</div>
<div class="navheader">
<span class="prev">
<a href="deb.html">« Install Elasticsearch with Debian Package</a>
</span>
<span class="next">
<a href="windows.html">Install Elasticsearch with Windows MSI Installer »</a>
</span>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="rpm"></a>Install Elasticsearch with RPM<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a>
</h2>
</div></div></div>
<p>The RPM for Elasticsearch can be <a class="xref" href="rpm.html#install-rpm" title="Download and install the RPM manually">downloaded from our website</a>
or from our  <a class="xref" href="rpm.html#rpm-repo" title="Installing from the RPM repository">RPM repository</a>. It can be used to install
Elasticsearch on any RPM-based system such as OpenSuSE, SLES, Centos, Red Hat,
and Oracle Enterprise.</p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>RPM install is not supported on distributions with old versions of RPM,
such as SLES 11 and CentOS 5.  Please see <a class="xref" href="targz.html" title="Install Elasticsearch from archive on Linux or MacOS">Install Elasticsearch from archive on Linux or MacOS</a> instead.</p>
</div>
</div>
<p>This package is free to use under the Elastic license. It contains open source
and free commercial features and access to paid commercial features.
<a href="/guide/en/kibana/7.7/managing-licenses.html" class="ulink" target="_top">Start a 30-day trial</a> to try out all of the
paid commercial features. See the
<a href="/subscriptions" class="ulink" target="_top">Subscriptions</a> page for information about
Elastic license levels.</p>
<p>The latest stable version of Elasticsearch can be found on the
<a href="/downloads/elasticsearch" class="ulink" target="_top">Download Elasticsearch</a> page. Other versions can
be found on the <a href="/downloads/past-releases" class="ulink" target="_top">Past Releases page</a>.</p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Elasticsearch includes a bundled version of <a href="http://openjdk.java.net" class="ulink" target="_top">OpenJDK</a>
from the JDK maintainers (GPLv2+CE). To use your own version of Java,
see the <a class="xref" href="setup.html#jvm-version" title="Java (JVM) Version">JVM version requirements</a></p>
</div>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-key"></a>Import the Elasticsearch PGP Key<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a>
</h3>
</div></div></div>
<p>We sign all of our packages with the Elasticsearch Signing Key (PGP key
<a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0xD27D666CD88E42B4" class="ulink" target="_top">D88E42B4</a>,
available from <a href="https://pgp.mit.edu" class="ulink" target="_top">https://pgp.mit.edu</a>) with fingerprint:</p>
<pre class="literallayout">4609 5ACC 8548 582C 1A26 99A9 D27D 666C D88E 42B4</pre>

<p>Download and install the public signing key:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch</pre>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-repo"></a>Installing from the RPM repository<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a>
</h3>
</div></div></div>
<p>Create a file called <code class="literal">elasticsearch.repo</code> in the <code class="literal">/etc/yum.repos.d/</code> directory
for RedHat based distributions, or in the <code class="literal">/etc/zypp/repos.d/</code> directory for
OpenSuSE based distributions, containing:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">[elasticsearch]
name=Elasticsearch repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=0
autorefresh=1
type=rpm-md</pre>
</div>
<p>And your repository is ready for use. You can now install Elasticsearch with one of the following commands:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo yum install --enablerepo=elasticsearch elasticsearch <a id="CO4-1"></a><i class="conum" data-value="1"></i>
sudo dnf install --enablerepo=elasticsearch elasticsearch <a id="CO4-2"></a><i class="conum" data-value="2"></i>
sudo zypper modifyrepo --enable elasticsearch &amp;&amp; \
  sudo zypper install elasticsearch; \
  sudo zypper modifyrepo --disable elasticsearch <a id="CO4-3"></a><i class="conum" data-value="3"></i></pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO4-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>Use <code class="literal">yum</code> on CentOS and older Red Hat based distributions.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO4-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>Use <code class="literal">dnf</code> on Fedora and other newer Red Hat distributions.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO4-3"><i class="conum" data-value="3"></i></a></p>
</td>
<td align="left" valign="top">
<p>Use <code class="literal">zypper</code> on OpenSUSE based distributions</p>
</td>
</tr>
</table>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>The configured repository is disabled by default. This eliminates the possibility of accidentally
upgrading <code class="literal">elasticsearch</code> when upgrading the rest of the system. Each install or upgrade command
must explicitly enable the repository as indicated in the sample commands above.</p>
</div>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>An alternative package which contains only features that are available under the
Apache 2.0 license is also available. To install it, use the following <code class="literal">baseurl</code> in your <code class="literal">elasticsearch.repo</code> file:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">baseurl=https://artifacts.elastic.co/packages/oss-7.x/yum</pre>
</div>
</div>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="install-rpm"></a>Download and install the RPM manually<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a>
</h3>
</div></div></div>
<p>The RPM for Elasticsearch v7.7.1 can be downloaded from the website and installed as follows:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.7.1-x86_64.rpm
wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.7.1-x86_64.rpm.sha512
shasum -a 512 -c elasticsearch-7.7.1-x86_64.rpm.sha512 <a id="CO5-1"></a><i class="conum" data-value="1"></i>
sudo rpm --install elasticsearch-7.7.1-x86_64.rpm</pre>
</div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO5-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>Compares the SHA of the downloaded RPM and the published checksum, which should output
<code class="literal">elasticsearch-{version}-x86_64.rpm: OK</code>.</p>
</td>
</tr>
</table>
</div>
<p>Alternatively, you can download the following package, which contains only
features that are available under the Apache 2.0 license:
<a href="https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-7.7.1-x86_64.rpm" class="ulink" target="_top">https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-oss-7.7.1-x86_64.rpm</a></p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>On systemd-based distributions, the installation scripts will attempt to set kernel parameters (e.g.,
<code class="literal">vm.max_map_count</code>); you can skip this by masking the systemd-sysctl.service unit.</p>
</div>
</div>
</div>

<div class="section xpack">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-enable-indices"></a>Enable automatic creation of system indices<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a><a class="xpack_tag" href="/subscriptions"></a>
</h3>
</div></div></div>
<p>Some commercial features automatically create indices within Elasticsearch.
By default, Elasticsearch is configured to allow automatic index creation, and no
additional steps are required. However, if you have disabled automatic index
creation in Elasticsearch, you must configure
<a class="xref" href="docs-index_.html#index-creation" title="Create indices automatically"><code class="literal">action.auto_create_index</code></a> in <code class="literal">elasticsearch.yml</code> to allow
the commercial features to create the following indices:</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">action.auto_create_index: .monitoring*,.watches,.triggered_watches,.watcher-history*,.ml*</pre>
</div>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<p>If you are using <a href="/products/logstash" class="ulink" target="_top">Logstash</a>
or <a href="/products/beats" class="ulink" target="_top">Beats</a> then you will most likely
require additional index names in your <code class="literal">action.auto_create_index</code> setting, and
the exact value will depend on your local configuration. If you are unsure of
the correct value for your environment, you may consider setting the value to
 <code class="literal">*</code> which will allow automatic creation of all indices.</p>
</div>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-sysv-init-vs-systemd"></a>SysV <code class="literal">init</code> vs <code class="literal">systemd</code><a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a>
</h3>
</div></div></div>
<p>Elasticsearch is not started automatically after installation. How to start
and stop Elasticsearch depends on whether your system uses SysV <code class="literal">init</code> or
<code class="literal">systemd</code> (used by newer distributions).  You can tell which is being used by
running this command:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">ps -p 1</pre>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-running-init"></a>Running Elasticsearch with SysV <code class="literal">init</code><a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm-init.asciidoc">edit</a>
</h3>
</div></div></div>
<p>Use the <code class="literal">chkconfig</code> command to configure Elasticsearch to start automatically
when the system boots up:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo chkconfig --add elasticsearch</pre>
</div>
<p>Elasticsearch can be started and stopped using the <code class="literal">service</code> command:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo -i service elasticsearch start
sudo -i service elasticsearch stop</pre>
</div>
<p>If Elasticsearch fails to start for any reason, it will print the reason for
failure to STDOUT. Log files can be found in <code class="literal">/var/log/elasticsearch/</code>.</p>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-running-systemd"></a>Running Elasticsearch with <code class="literal">systemd</code><a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/systemd.asciidoc">edit</a>
</h3>
</div></div></div>
<p>To configure Elasticsearch to start automatically when the system boots up,
run the following commands:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo /bin/systemctl daemon-reload
sudo /bin/systemctl enable elasticsearch.service</pre>
</div>
<p>Elasticsearch can be started and stopped as follows:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo systemctl start elasticsearch.service
sudo systemctl stop elasticsearch.service</pre>
</div>
<p>These commands provide no feedback as to whether Elasticsearch was started
successfully or not. Instead, this information will be written in the log
files located in <code class="literal">/var/log/elasticsearch/</code>.</p>
<p>If you have password-protected your Elasticsearch keystore, you will need to provide
<code class="literal">systemd</code> with the keystore password using a local file and systemd environment
variables. This local file should be protected while it exists and may be
safely deleted once Elasticsearch is up and running.</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">echo "keystore_password" &gt; /path/to/my_pwd_file.tmp
chmod 600 /path/to/my_pwd_file.tmp
sudo systemctl set-environment ES_KEYSTORE_PASSPHRASE_FILE=/path/to/my_pwd_file.tmp
sudo systemctl start elasticsearch.service</pre>
</div>
<p>By default the Elasticsearch service doesn’t log information in the <code class="literal">systemd</code>
journal. To enable <code class="literal">journalctl</code> logging, the <code class="literal">--quiet</code> option must be removed
 from the <code class="literal">ExecStart</code> command line in the <code class="literal">elasticsearch.service</code> file.</p>
<p>When <code class="literal">systemd</code> logging is enabled, the logging information are available using
the <code class="literal">journalctl</code> commands:</p>
<p>To tail the journal:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo journalctl -f</pre>
</div>
<p>To list journal entries for the elasticsearch service:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo journalctl --unit elasticsearch</pre>
</div>
<p>To list journal entries for the elasticsearch service starting from a given time:</p>
<div class="pre_wrapper lang-sh">
<pre class="programlisting prettyprint lang-sh">sudo journalctl --unit elasticsearch --since  "2016-10-30 18:17:16"</pre>
</div>
<p>Check <code class="literal">man journalctl</code> or <a href="https://www.freedesktop.org/software/systemd/man/journalctl.html" class="ulink" target="_top">https://www.freedesktop.org/software/systemd/man/journalctl.html</a> for
more command line options.</p>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-check-running"></a>Checking that Elasticsearch is running<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/check-running.asciidoc">edit</a>
</h3>
</div></div></div>
<p>You can test that your Elasticsearch node is running by sending an HTTP
request to port <code class="literal">9200</code> on <code class="literal">localhost</code>:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">GET /</pre>
</div>
<div class="console_widget" data-snippet="snippets/16.console"></div>
<p>which should give you a response something like this:</p>
<div class="pre_wrapper lang-js">
<pre class="programlisting prettyprint lang-js">{
  "name" : "Cp8oag6",
  "cluster_name" : "elasticsearch",
  "cluster_uuid" : "AT69_T_DTp-1qgIJlatQqA",
  "version" : {
    "number" : "7.7.1",
    "build_flavor" : "default",
    "build_type" : "tar",
    "build_hash" : "f27399d",
    "build_date" : "2016-03-30T09:51:41.449Z",
    "build_snapshot" : false,
    "lucene_version" : "8.5.1",
    "minimum_wire_compatibility_version" : "1.2.3",
    "minimum_index_compatibility_version" : "1.2.3"
  },
  "tagline" : "You Know, for Search"
}</pre>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-configuring"></a>Configuring Elasticsearch<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a>
</h3>
</div></div></div>
<p>Elasticsearch defaults to using <code class="literal">/etc/elasticsearch</code> for runtime configuration.
The ownership of this directory and all files in this directory are set to
<code class="literal">root:elasticsearch</code> on package installation and the directory has the <code class="literal">setgid</code>
flag set so that any files and subdirectories created under <code class="literal">/etc/elasticsearch</code>
are created with this ownership as well (e.g., if a keystore is created using
the <a class="xref" href="secure-settings.html" title="Secure settings">keystore tool</a>). It is expected that this be maintained so
that the Elasticsearch process can read the files under this directory via the
group permissions.</p>
<p>Elasticsearch loads its configuration from the
<code class="literal">/etc/elasticsearch/elasticsearch.yml</code> file by default.  The format of this
config file is explained in <a class="xref" href="settings.html" title="Configuring Elasticsearch"><em>Configuring Elasticsearch</em></a>.</p>
<p>The RPM also has a system configuration file (<code class="literal">/etc/sysconfig/elasticsearch</code>),
which allows you to set the following parameters:</p>
<div class="informaltable">
<table border="0" cellpadding="4px">
<colgroup>
<col>
<col>
</colgroup>
<tbody valign="top">
<tr>
<td valign="top">
<p>
<code class="literal">JAVA_HOME</code>
</p>
</td>
<td valign="top">
<p>
Set a custom Java path to be used.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p>
<code class="literal">MAX_OPEN_FILES</code>
</p>
</td>
<td valign="top">
<p>
Maximum number of open files, defaults to <code class="literal">65535</code>.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p>
<code class="literal">MAX_LOCKED_MEMORY</code>
</p>
</td>
<td valign="top">
<p>
Maximum locked memory size. Set to <code class="literal">unlimited</code> if you use the
<code class="literal">bootstrap.memory_lock</code> option in elasticsearch.yml.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p>
<code class="literal">MAX_MAP_COUNT</code>
</p>
</td>
<td valign="top">
<p>
Maximum number of memory map areas a process may have. If you use <code class="literal">mmapfs</code>
as index store type, make sure this is set to a high value. For more
information, check the
<a href="https://github.com/torvalds/linux/blob/master/Documentation/sysctl/vm.txt" class="ulink" target="_top">linux kernel documentation</a>
about <code class="literal">max_map_count</code>. This is set via <code class="literal">sysctl</code> before starting
Elasticsearch. Defaults to <code class="literal">262144</code>.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p>
<code class="literal">ES_PATH_CONF</code>
</p>
</td>
<td valign="top">
<p>
Configuration file directory (which needs to include <code class="literal">elasticsearch.yml</code>,
<code class="literal">jvm.options</code>, and <code class="literal">log4j2.properties</code> files); defaults to
<code class="literal">/etc/elasticsearch</code>.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p>
<code class="literal">ES_JAVA_OPTS</code>
</p>
</td>
<td valign="top">
<p>
Any additional JVM system properties you may want to apply.
</p>
</td>
</tr>
<tr>
<td valign="top">
<p>
<code class="literal">RESTART_ON_UPGRADE</code>
</p>
</td>
<td valign="top">
<p>
Configure restart on package upgrade, defaults to <code class="literal">false</code>. This means you
will have to restart your Elasticsearch instance after installing a
package manually. The reason for this is to ensure, that upgrades in a
cluster do not result in a continuous shard reallocation resulting in high
network traffic and reducing the response times of your cluster.
</p>
</td>
</tr>
</tbody>
</table>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Distributions that use <code class="literal">systemd</code> require that system resource limits be
configured via <code class="literal">systemd</code> rather than via the <code class="literal">/etc/sysconfig/elasticsearch</code>
file.  See <a class="xref" href="setting-system-settings.html#systemd" title="Systemd configuration">Systemd configuration</a> for more information.</p>
</div>
</div>
</div>

<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="rpm-layout"></a>Directory layout of RPM<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/rpm.asciidoc">edit</a>
</h3>
</div></div></div>
<p>The RPM places config files, logs, and the data directory in the appropriate
locations for an RPM-based system:</p>
<div class="informaltable">
<table border="1" cellpadding="4px">
<colgroup>
<col class="col_1">
<col class="col_2">
<col class="col_3">
<col class="col_4">
</colgroup>
<thead>
<tr>
<th align="left" valign="top">Type</th>
<th align="left" valign="top">Description</th>
<th align="left" valign="top">Default Location</th>
<th align="left" valign="top">Setting</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>home</strong></span></p></td>
<td align="left" valign="top"><p>Elasticsearch home directory or <code class="literal">$ES_HOME</code></p></td>
<td align="left" valign="top"><p><code class="literal">/usr/share/elasticsearch</code></p></td>
<td align="left" valign="top"><p></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>bin</strong></span></p></td>
<td align="left" valign="top"><p>Binary scripts including <code class="literal">elasticsearch</code> to start a node
    and <code class="literal">elasticsearch-plugin</code> to install plugins</p></td>
<td align="left" valign="top"><p><code class="literal">/usr/share/elasticsearch/bin</code></p></td>
<td align="left" valign="top"><p></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>conf</strong></span></p></td>
<td align="left" valign="top"><p>Configuration files including <code class="literal">elasticsearch.yml</code></p></td>
<td align="left" valign="top"><p><code class="literal">/etc/elasticsearch</code></p></td>
<td align="left" valign="top"><p><code class="literal"><a class="xref" href="settings.html#config-files-location" title="Config files location">ES_PATH_CONF</a></code></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>conf</strong></span></p></td>
<td align="left" valign="top"><p>Environment variables including heap size, file descriptors.</p></td>
<td align="left" valign="top"><p><code class="literal">/etc/sysconfig/elasticsearch</code></p></td>
<td align="left" valign="top"><p></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>data</strong></span></p></td>
<td align="left" valign="top"><p>The location of the data files of each index / shard allocated
    on the node. Can hold multiple locations.</p></td>
<td align="left" valign="top"><p><code class="literal">/var/lib/elasticsearch</code></p></td>
<td align="left" valign="top"><p><code class="literal">path.data</code></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>jdk</strong></span></p></td>
<td align="left" valign="top"><p>The bundled Java Development Kit used to run Elasticsearch. Can
    be overridden by setting the <code class="literal">JAVA_HOME</code> environment variable
    in <code class="literal">/etc/sysconfig/elasticsearch</code>.</p></td>
<td align="left" valign="top"><p><code class="literal">/usr/share/elasticsearch/jdk</code></p></td>
<td align="left" valign="top"><p></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>logs</strong></span></p></td>
<td align="left" valign="top"><p>Log files location.</p></td>
<td align="left" valign="top"><p><code class="literal">/var/log/elasticsearch</code></p></td>
<td align="left" valign="top"><p><code class="literal">path.logs</code></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>plugins</strong></span></p></td>
<td align="left" valign="top"><p>Plugin files location. Each plugin will be contained in a subdirectory.</p></td>
<td align="left" valign="top"><p><code class="literal">/usr/share/elasticsearch/plugins</code></p></td>
<td align="left" valign="top"><p></p></td>
</tr>
<tr>
<td align="left" valign="top"><p><span class="strong strong"><strong>repo</strong></span></p></td>
<td align="left" valign="top"><p>Shared file system repository locations. Can hold multiple locations. A file system repository can be placed in to any subdirectory of any directory specified here.</p></td>
<td align="left" valign="top"><p>Not configured</p></td>
<td align="left" valign="top"><p><code class="literal">path.repo</code></p></td>
</tr>
</tbody>
</table>
</div>
</div>

<div class="section exclude">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_next_steps_4"></a>Next steps<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/setup/install/next-steps.asciidoc">edit</a>
</h3>
</div></div></div>
<p>You now have a test Elasticsearch environment set up.  Before you start
serious development or go into production with Elasticsearch, you must do some additional
setup:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
Learn how to <a class="xref" href="settings.html" title="Configuring Elasticsearch">configure Elasticsearch</a>.
</li>
<li class="listitem">
Configure <a class="xref" href="important-settings.html" title="Important Elasticsearch configuration">important Elasticsearch settings</a>.
</li>
<li class="listitem">
Configure <a class="xref" href="system-config.html" title="Important System Configuration">important system settings</a>.
</li>
</ul>
</div>
</div>

</div>
<div class="navfooter">
<span class="prev">
<a href="deb.html">« Install Elasticsearch with Debian Package</a>
</span>
<span class="next">
<a href="windows.html">Install Elasticsearch with Windows MSI Installer »</a>
</span>
</div>
</div>

                  <!-- end body -->
                </div>
                <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                  <div id="rtpcontainer" style="display: block;">
                    <div class="mktg-promo">
                      <h3>Most Popular</h3>
                      <ul class="icons">
                        <li class="icon-elasticsearch-white"><a href="https://www.elastic.co/webinars/getting-started-elasticsearch?baymax=default&amp;elektra=docs&amp;storm=top-video">Get Started with Elasticsearch: Video</a></li>
                        <li class="icon-kibana-white"><a href="https://www.elastic.co/webinars/getting-started-kibana?baymax=default&amp;elektra=docs&amp;storm=top-video">Intro to Kibana: Video</a></li>
                        <li class="icon-logstash-white"><a href="https://www.elastic.co/webinars/introduction-elk-stack?baymax=default&amp;elektra=docs&amp;storm=top-video">ELK for Logs &amp; Metrics: Video</a></li>
                      </ul>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </section>

        </div>


<div id="elastic-footer"></div>
<script src="https://www.elastic.co/elastic-footer.js"></script>
<!-- Footer Section end-->

      </section>
    </div>

<script src="/guide/static/jquery.js"></script>
<script type="text/javascript" src="/guide/static/docs.js"></script>
<script type="text/javascript">
  window.initial_state = {}</script>
  </body>
</html>
